I also noticed this, as I stepped into the shower. Could it be that the AI is smart enough to figure it out?

Often things take longer than you think. Do it right.

Found it at: https://developer.apple.com/documentation/createmlcomponents/counting_human_body_action_repetitions_in_a_live_video_feed

This watch, now devoid of developer profiles, and running standard released 7.5, with no profiles what so ever, when trying to upgrade to 7.6 ( released yesterday), ..... ... behaves identically. It throws the error Unable to Verify Update. The watchOS update couldn't be verified because you are not connected to the Internet. Still stuck in 7.5, although the world has moved on to 7.6

Factory reset, retry - same problem. I'm gonna have to learn to love watchOS 7.5 I am wondering, watchOS 8 is billed as "always on", a feature introduced in Series 5 watches. My watch is a Series 4, and is not normally "always on". I was wondering about the battery drain of the beta. Perhaps I am spared the experience of watchOS 8 betas, due to old hardware. Does anyone know if watchOS 8 runs on "not always on" hardware like my Series 4?

Un-pair, re-pair, set up as new - same problem

Read the Friendly Manual! from release notes for 12.4: Known Issues Xcode may hang if the host Mac is connected to an iOS device which has one or more companion watches. The hangs occur when the watches aren't fully prepared for development, or if they are experiencing poor wireless connectivity. (72490921) (FB8945320) Workaround: Power off the watches, or unpair them from the iPhone. You can force Xcode to freshly prepare a watch for development using these steps: